Skip to content

fix(release): release whenever main is ahead of the registry - #214

Merged
muscariello merged 1 commit into
mainfrom
fix/release-always
Sep 4, 2026
Merged

muscariello merged 1 commit into
mainfrom
fix/release-always

Conversation

@muscariello

@muscariello muscariello commented Sep 4, 2026

Copy link
Copy Markdown
Member

release_always = true retries on the next push. Idempotent: it publishes only while a version is ahead of the registry.

@muscariello
muscariello requested a review from a team as a code owner September 4, 2026 14:32
@muscariello
muscariello requested a review from tkircsi September 4, 2026 14:32
@codecov

codecov Bot commented Sep 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

#207 bumped the workspace to 0.1.7 and merged, but its publish run failed on
the Trusted Publishing requirement #208 later fixed. With release_always =
false nothing retried it: release skipped every later push, and release-pr
would not bump past a version crates.io has not seen.

Signed-off-by: Luca Muscariello <muscariello@ieee.org>
@muscariello
muscariello requested review from msardara and removed request for tkircsi September 4, 2026 15:41
@muscariello
muscariello merged commit 4c510b4 into main Sep 4, 2026
17 checks passed
@muscariello
muscariello deleted the fix/release-always branch September 4, 2026 16:20
muscariello added a commit that referenced this pull request Sep 4, 2026
Reverts #214 now that 0.1.7 is published and main matches crates.io, so
nothing is stranded. Keeps publishing tied to merging the release PR, which
is the point where a release is decided.

#214 was to unstick a release whose publish had failed; if that happens
again, flipping this to true for one push retries it.

Signed-off-by: Luca Muscariello <muscariello@ieee.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants